System and/or method for downstream bidding

ABSTRACT

Disclosed are systems and/or apparatuses of transmitting digital objects to a destination. In particular, disclosed are systems and/or apparatuses of facilitating bidding for the business of forwarding digital objects in a data transmission network.

BACKGROUND

1. Field

The subject matter disclosed herein relates to the transmission ofdigital objects in a data transmission network.

2. Information

Information exchange mechanisms using the Internet have been availablefor free for many services. To forward information from a source node toa destination node, one or more intermediary parties may forward theinformation over at least a portion of a path coupling the source nodeto the destination node. Such intermediary parties typically own, lease,control and/or operate equipment such as routers and/or the like forforwarding information according to a network protocol such as theInternet Protocol. The intermediary parties incur substantial costs inthe deployment, maintenance and operation of equipment for the purposeof forwarding information to a destination node.

BRIEF DESCRIPTION OF THE FIGURES

Non-limiting and non-exhaustive embodiments of the present inventionwill be described with reference to the following figures, wherein likereference numerals refer to like parts throughout the various figuresunless otherwise specified.

FIG. 1 is a schematic diagram of a data transmission network accordingto an embodiment.

FIG. 2 is a schematic diagram of a router that may be owned, leased,controlled and/or operated by an intermediary for transmitting at leasta portion of a digital object to a destination node according to anembodiment.

FIG. 3 is schematic diagram of a data transmission network fortransmitting a digital object to two or more destination nodes accordingto an embodiment.

FIG. 4 is a flow diagram illustrating a process to initiate transmissionof a digital object from a source node according to an embodiment.

FIG. 5 is a flow diagram illustrating a process to act upon a bidrequest received at an intermediary according to an embodiment.

FIG. 6 is a schematic diagram of a data transmission network fortransmitting a digital object from a source node to a destination nodethrough two or more intermediaries.

FIG. 7 is a flow diagram illustrating a process to act upon a bidrequest received at an intermediary according to an embodiment.

FIG. 8 is a schematic diagram of a data transmission network comprisinga first network to transmit a digital object from a source node to adestination node and second network to facilitate bidding amongintermediaries.

FIG. 9 is a flow diagram illustrating a process to initiate transmissionof a digital object to one or more destination nodes according to anembodiment of the data transmission network of FIG. 8.

FIG. 10 is a flow diagram illustrating a process to facilitate biddingfor the service of forwarding a digital object to one or moredestination nodes according to an embodiment of the data transmissionnetwork of FIG. 8.

DETAILED DESCRIPTION

Reference throughout this specification to “one embodiment” or “anembodiment” means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment of the present invention. Thus, theappearances of the phrase “in one embodiment” or “an embodiment” invarious places throughout this specification are not necessarily allreferring to the same embodiment. Furthermore, the particular features,structures, or characteristics may be combined in one or moreembodiments.

A “data transmission network” as referred to herein relates toinfrastructure that is capable of transmitting data among nodes whichare coupled to the data transmission network. For example, a datatransmission network may comprise links capable of transmitting databetween nodes according to one or more data transmission protocols. Suchlinks may comprise one or more types of transmission media capable oftransmitting information from a source to a destination. However, theseare merely examples of a data transmission network and claimed subjectmatter is not limited in these respects.

In the transmission of data in a data transmission network, a “sourcenode” may initiate transmission of data to one or more “destinationnodes” coupled to the data transmission network. In one particularembodiment, although the claimed subject matter is not limited in thisrespect, a source node may initiate the transmission of data to thedestination node based, at least in part, upon a destination addressassociated with the destination node. Here, according to a communicationprotocol of a particular embodiment, the source node may transmit datato the destination node in one or more “data packets” which are routedto the destination node through the data transmission network based, atleast in part, on the destination address. However, these are merelyexamples of how data may be transmitted from a source node to adestination node in a data transmission network and claimed subjectmatter is not limited in these respects.

A node in a data transmission network may “forward” information to oneor more other nodes in the data transmission network over data links. Inone particular example, a first node may forward information to a secondnode by transmitting one or more data packets according to acommunication protocol. Such data packets may comprise a header portioncontaining an address of an intended destination node and a payloadcontaining forwarded information. If the second node is not the ultimateintended destination, the second node may also forward the data packetsto a third node which comprises and/or is coupled to the ultimateintended destination node. However, these merely examples of howinformation may be forwarded in a data transmission network and claimedsubject matter is not limited in these respects.

A “digital object” as referred to herein relates to information that isorganized and/or formatted in a digitized form. For example, a digitalobject may comprise one or more documents, visual media and/or audiomedia, and/or combinations thereof. However, these are merely examplesof the types of information that may be maintained in a digital objectand claimed subject matter is not limited in this respect. Such adigital object may be maintained in a compressed format to enableefficient storage of the digital object in a storage medium and/ortransmission of the digital in a data transmission network. In otherembodiments, such a digital object may be encrypted for transmission ina secure communication channel. In one particular embodiment, althoughthe claimed subject matter is not limited in this respect, a digitalobject may be formatted at a source node for transmission to one or moredestination nodes. Also, a digital object may be transmitted to one ormore destination nodes as one or more data packets routed to the one ormore data nodes according to a communication protocol. However, theseare merely examples of a digital object and claimed subject matter isnot limited in these respects.

A “bid” as referred to herein relates to an expression of a proposal toperform a service. In one particular example, a customer and/or clientmay receive bids from more than one party competing for the business ofthe customer and/or client. A bid may specify terms under which aservice may be performed such as, for example, price, quality,timeliness and/or reliability. However, these are merely examples ofterms that may be expressed in a bid and claimed subject matter is notlimited in this respect. Also, in some commercial contexts, acceptanceof a bid by a customer and/or client may be binding on the parties. Inother commercial contexts, however, acceptance of a bid by a customerand/or client, in and of itself, may not be binding. Here, additionalactions by one or more parties may result in a binding arrangement. Itshould be understood that these are merely examples of a bid and claimedsubject matter is not limited in this respect.

A “bid request” as referred to herein relates to an expression of aninvitation to provide a bid for performing a service. In one particularexample, such a bid request may specify a desired service to beperformed by a service provider. In some embodiments, the bid requestmay specify some of the terms, but not necessarily all of the terms,under which a desired service is to be performed. However, these aremerely examples of a bid request and claimed subject matter is notlimited in these respects.

In response to receipt of a bid from a service provider for providing aservice, a potential customer and/or client may provide an “acceptancemessage” to the bidding service provider. Such an acceptance message mayexpress a willingness of the customer and/or client to receive servicesfrom the service provider according to at least some terms set forth inthe received bid. However, this is merely an example of an acceptancemessage and the claimed subject matter is not limited in this respect.

According to an embodiment, two or more parties may exchange messages inthe course of agreeing to terms under which a service maybe providedaccording to a “negotiation protocol.” In one particular embodiment,although claimed subject matter is not limited in this respect, anegotiation protocol may define how parties express a bid, bid requestand/or acceptance message. In another embodiment, parties may exchangemessages according to a negotiation protocol until a particularpredefined state and/or event defining closure. Here, such a closure maydefine agreed terms under which a service is to be provided. It shouldbe understood, however, that these are merely examples of a negotiationprotocol and claimed subject matter is not limited in these respects.

In forwarding a digital object from a source node to a destination nodeover a data transmission network, equipment which is owned, leased,controlled and/or operated by one or more “intermediaries” or“intermediary parties” may forward at least a portion of the digitalobject over at least a portion of the data transmission network towardthe destination node. As illustrated below, the term “intermediary” mayrefer to a party that may forward a digital object over at least aportion of the data transmission network and/or equipment that is owned,leased, controlled and/or operated by the party for performing thisservice.

Equipment that is owned, leased, controlled and/or maintained by anintermediary may comprise equipment that is capable of transmittinginformation to and/or receiving information a data transmission network.Here, such equipment may comprise one or more “communication ports”capable of receiving information from a source node and/or transmittinginformation to a destination node over one or more data transmissionmediums forming links in the data transmission network. Such acommunication port may be capable of transmitting and/or receivinginformation from any one of several types of data transmission mediasuch as, for example, cabling (e.g., optical, coaxial, unshieldedtwisted wire pair cabling, etc.) and/or wireless transmission media(e.g., by terrestrial or satellite links). However, these are merelyexamples of a communication port that may couple equipment which isowned, leased controlled and/or operated by an intermediary to a datatransmission network, and claimed subject matter is not limited in theserespects.

“Instructions” as referred to herein relate to expressions whichrepresent one or more logical operations. For example, instructions maybe “machine-readable” by being interpretable by a machine for executingone or more operations on one or more data objects. However, this ismerely an example of instructions and claimed subject matter is notlimited in this respect. In another example, instructions as referred toherein may relate to encoded commands which are executable by aprocessing circuit having a command set which includes the encodedcommands. Such an instruction may be encoded in the form of a machinelanguage understood by the processing circuit. Again, these are merelyexamples of an instruction and claimed subject matter is not limited inthis respect.

“Storage medium” as referred to herein relates to media capable ofmaintaining expressions which are perceivable by one or more machines.For example, a storage medium may comprise one or more storage devicesfor storing machine-readable instructions and/or information. Suchstorage devices may comprise any one of several media types including,for example, magnetic, optical or semiconductor storage media. However,these are merely examples of a storage medium and claimed subject matteris not limited in these respects.

“Logic” as referred to herein relates to structure for performing one ormore logical operations. For example, logic may comprise circuitry whichprovides one or more output signals based upon one or more inputsignals. Such circuitry may comprise a finite state machine whichreceives a digital input and provides a digital output, or circuitrywhich provides one or more analog output signals in response to one ormore analog and/or digital input signals. Such circuitry may be providedin an application specific integrated circuit (ASIC) or fieldprogrammable gate array (FPGA). Also, logic may comprisemachine-readable instructions stored in a storage medium in combinationwith processing circuitry to execute such machine-readable instructions.However, these are merely examples of structures which may provide logicand claimed subject matter is not limited in this respect.

An “agent” as referred to herein relates to a process that executes on afirst device and is capable of communicating with a second device over adata transmission network. In one particular embodiment, for example, anagent process may collect information associated with the first deviceand enable transmission of the collected information to the seconddevice. In another embodiment, an agent may receive control signals fromthe second device to enable remote control of at least one aspect of thefirst device. However, these are merely examples of how an agent mayenable communication between devices and the claimed subject matter isnot limited in these respects. In another embodiment, an agent mayexecute on a processor under the control of machine-readableinstructions stored on a storage medium. In another embodiment, an agentmay be executed on different types of structure that provide logic.However, these are merely examples of an agent and claimed subjectmatter is not limited in these respects.

A “quality of service” (“QoS”) as referred to herein relates to acharacteristic of a data transmission service to provide data to arecipient within particular constraints. In particular examples,although claimed subject matter is not limited in this respect, QoS mayrefer to delivery of a service within expected bandwidth constraints,time constraints and/or error constraints. A quality of service mayrefer to a characteristic of a transmission control protocol/internetprotocol (TCP/IP) type protocol, and/or a user datagramprotocol/internet protocol (UDP/IP) type protocol. In one or moreembodiments, a quality of service may refer to a threshold errortransmission rate, for example where one or more data packets may notarrive, and/or where one or more data packets that do arrive may includeone or more corrupted bits of information. In one or more embodiments, aquality of service may refer to where no errors and/or no error rate isacceptable, and/or to a threshold where the number of errors and/or theerror rate may not exceed a predetermined value, and/or to a rangewithin which a number of errors and/or an error rate may be acceptable,although the scope of claimed subject matter is not limited in thisrespect. In a particular embodiment, for example, a QoS may beassociated with the transmission of a digital object from a source nodeto a destination node. Here, for example, a QoS may dictate that all ora portion of the digital object arrive at the destination node within adefined bandwidth limits, and/or within some time constraint, and/orwith or without number of errors and/or within error rate limits. Inanother embodiment, a QoS may define, at least in part, an effectivedata rate at which a digital object is to be transmitted to thedestination node. However, this is merely an example of how QoS may beapplied in the transmission of a digital object and claimed subjectmatter is not limited in this respect.

Unless specifically stated otherwise, as apparent from the followingdiscussion, it is appreciated that throughout this specificationdiscussions utilizing terms such as “processing,” “computing,”“calculating,” “selecting, “forming,” “enabling,” “inhibiting,”“identifying,” “initiating,” “receiving,” “transmitting,” “determining”and/or the like refer to the actions and/or processes that may beperformed by a computing platform, such as a computer or a similarelectronic computing device, thatqmanipulates and/or transforms datarepresented as physical electronic and/or magnetic quantities and/orother physical quantities within the computing platform's processors,memories, registers, and/or other information storage, transmission,reception and/or display devices. Further, unless specifically statedotherwise, process described herein, with reference to flow diagrams orotherwise, may also be executed and/or controlled, in whole or in part,by such a computing platform.

FIG. 1 is a schematic diagram of a data transmission network 25according to an embodiment. A source node 2 and destination nodes 18through 24 may access data transmission network 25 using any one ofseveral data transmission access technologies such as, for example,public switched telephone network (PSTN), digital subscriber line (DSL),coaxial/optical cable or wireless access (e.g., using satellite and/orterrestrial links). However, these are merely examples of how a node mayobtain access to a data transmission network and claimed subject matteris not limited in these respects. Data transmission network 25 may becapable of transmitting data packets among nodes in a network topologyaccording to an Internet Protocol (IP). However, this is merely anexample of a communication protocol that may be used in transmission ofall or portions of a digital object from a source node to a destinationnode and claimed subject matter is not limited in this respect. Here, ina particular embodiment illustrated in FIG. 1, source node 2 anddestination nodes 18 through 24 may access data network 25 through thefacilities of Internet service providers (ISPs) 10 and 16. For example,source node 2 and/or destination nodes 18 through 24 may comprisesubscribers of corresponding ISPs that enable access to datatransmission network 25 for a subscription fee. However, an ISP ismerely an example of how a source and/or destination node may access adata transmission network and claimed subject matter is not limited inthis respect.

According to an embodiment, source node 2 and/or destination nodes 18through 24 may comprise any one of several types of devices which arecapable of transmitting and/or receiving digital objects. In oneparticular example, source node and/or destination nodes 18 through 24may comprise a communication port (not shown) that is adapted fortransmitting data to and/or receiving data from an ISP through a datatransmission medium using one or more of the aforementioned accesstechnologies. In addition to communication ports, source node 2 and/ordestination nodes 18 through 24 may also comprise a computing platformemploying a processor, one or more memory devices and appropriateinput/output devices for communicating between processes executing onthe processor and communication ports. Here, such processes executing ona computing platform may be controlled, at least in part, bymachine-readable instructions stored in one or more memory devices ofthe computing platform. In one particular embodiment, a computingplatform at source node 2 may execute one or more processes to createand/or format a digital object for transmission on data transmissionnetwork 25. However, this is merely an example of how a source node 2may create and/or format a digital object for transmission on a datatransmission network and claimed subject matter is not limited in thisrespect. In another particular embodiment, a computing platform at adestination node may execute one or more processes to utilize a digitalobject received from data transmission network 25 through acommunication port. However, this is merely an example of how adestination node may process a digital object received from a datatransmission network and claimed subject matter is not limited in thisrespect.

According to an embodiment, equipment that is owned, leased, controlledand/or operated by intermediaries 12 may transmit digital objectsbetween ISPs 10 and 16. Links coupling the intermediary equipment toISPs 10 and 16 may comprise any one of several data transmission mediumssuch as, for example, cabling (e.g., fiber optic, coaxial and/orunshielded twisted wire pair cabling) and/or wireless transmission media(e.g., using terrestrial and/or satellite based links). However, theseare merely examples of transmission media that may be used to transmitdigital objects in a data transmission network and claimed subjectmatter is not limited in these respects.

As illustrated in FIG. 1, ISP 10 may transmit a digital object to ISP 16in any one of multiple paths comprising at least one correspondingintermediary 12. Here, according to a particular embodiment, ISP 10 maytransmit a digital object to ISP 16 through any one of theintermediaries 12a, 12b and/or 12c. As discussed below, according to aparticular embodiment, source node 2 and/or ISP 10 may select aparticular intermediary 12 to forward the digital object to the ISP 16based, at least in part, upon one or more bids received fromintermediaries 12 a, 12 b and/or 12 c. However, this is merely anexample of how an intermediary may be selected for forwarding a digitalobject and claimed subject matter is not limited in this respect.

According to an embodiment, although claimed subject matter in notlimited in this respect, intermediaries 12 may route digital objectsbetween ISPs 10 and 16 in one or more data packets formatted accordingto a particular network protocol such as an Internet Protocol (IP). Suchdata packets may be forwarded on data links connecting intermediaries 12and ISPs according to any one of several data link layer protocols suchas, for example, Ethernet, Asynchronous Transfer Mode (ATM), Frame Relayand/or Synchronous Optical NETwork/Sychronous Digital Hierarchy(SONET/SDH) data link protocols. In embodiments employing wirelesscommunication links, data packets may be forwarded on such wirelesscommunication links according to any one of several satellite and/orterrestrial wireless data link protocols such as, for example, IEEEStds. 802.11, and 802.16. However, these are merely examples of datalink protocols that may be used to forward data packets in a datatransmission network and claimed subject matter is not limited in thisrespect.

According to an embodiment, an intermediary 12 may comprise one or morerouters for forwarding data packets originating at source node 2 todestination nodes. FIG. 2 is a schematic diagram of a router 28 whichmay be owned, leased and/or operated at an intermediary for transmittingat least a portion of a digital object to a destination node accordingto an embodiment. Router 28 may comprise one or more ingresscommunication ports 24 to receive data packet communications accordingto one or more of the aforementioned protocols. Here, one or more ofingress communication ports 24 may be capable of receiving all or aportion of a digital object from ISP 10 (and originating at source node2). Router 28 may also comprise one or more egress communication ports26 to transmit data packet communications according to one or more ofthe aforementioned protocols. Here, one or more of egress communicationports 26 may be capable of transmitting all or a portion of a digitalobject to ISP 16 (to then be forwarded to one or more destinationnodes).

According to an embodiment, router 28 may comprise logic to determinehow to forward packets received on ingress communication ports 24 toegress communication ports 26. For example, router 28 may determine anegress communication port 26 for forwarding a received data packetbased, at least in part, on information associated with the receiveddata packet such as, for example, a destination address. Here, accordingto a particular embodiment, router 28 may determine an egress port 26for forwarding the received data packet according to one or more look uptables associating destination IP address with egress ports 26. However,this is merely an example of how a router may determine an egress portfor forwarding a data packet and claimed subject matter is not limitedin this respect. Notwithstanding the existence of a valid destinationaddress associated with a received data packet, according to anembodiment, router 28 may also select whether or not to forward areceived data packet based, at least in part, on information such asdestination and/or source associated with the data packet, or otherinformation associated with the data packet.

According to an embodiment, the aforementioned logic of router 28 tocontrol routing data packets from an ingress communication port 24 to anegress communication port 26 may comprise one or more computingplatforms comprising one or more processors and memory devices. Thememory devices may comprise machine-readable instructions to execute onthe one or more processors for controlling the routing of data packets.Alternatively, router 28 may comprise one or more ASIC devices tocontrol routing, and/or combinations of one or more ASIC devices and oneor more computing platforms to control routing. However, these aremerely examples of logic that may be employed in a router forcontrolling forwarding of data packets and claimed subject matter is notlimited in these respects.

According to an embodiment, an intermediary 12 (FIG. 1) may employ morethan one router 28 to forward a digital object to a destination node. Adigital object received from source node 2 at a first router may beforwarded to a second router where both first and second routers areowned, leased, controlled and/or operated by intermediary 12. Here, thefirst router may receive the digital object from the ISP 10 and forwardthe received digital object to the second router either directly to thesecond router or via one or more other routing devices. The secondrouter may then forward to ISP 16 the digital object received from thefirst router. However, this is merely an example of how an intermediarymay employ multiple routers for forwarding a digital object from asource node to a destination node, and claimed subject matter is notlimited in this respect.

According to an embodiment, the intermediaries 12 and/or ISPs 10 and 16may employ multiprotocol label switching (MPLS) according to the MPLSArchitecture set forth in Internet Engineering Task Force (IETF),Network Working Group, RFC 3031, 2001. Here, ISP 10 may comprise a“label edge router” (LER) that is capable of assigning label values topackets received from source node 2 for transmission to a destinationnode. One or more routers of the intermediaries 12 may comprise a “labelswitch router” (LSR) to make forwarding decisions for received datapackets based, at least in part, upon label values assigned to thereceived data packets. At a network hop between ISP 10 and ISP 16, anLSR associated with an intermediary 12 may strip off an existing labelof a received data packet and apply a new label indicating how the nextdownstream LSR is to forward the data packet to a destination. LSRscoupled to forward a digital object from ISP 10 to ISP 16 may then forma Label Switch Path (LSP) determined, at least in part, according tolabels (e.g., selected from a hierarchy of labels such as a label stack)assigned to data packets transporting a digital object at network hopsbetween ISP 10 and ISP 16. However, this is merely an example of how adigital object may be transmitted between nodes on a data transmissionnetwork using MPLS and claimed subject matter is not limited in theserespects.

FIG. 3 is schematic diagram of a data transmission network 100 fortransmitting a digital object to two or more destination nodes accordingto an embodiment. A source node 102 may transmit a digital object tomore than one destination node coupled to one or more ISPs 116. Two ormore intermediaries 112 may then be employed to forward the digitalobject to two or more destinations. According to an embodiment, adigital object formatted for transmission to a destination node may becopied at either the ISP 110 or an intermediary 112 for transmission tomultiple destinations.

According to an embodiment, a digital object may be segmented and/orpartitioned in to smaller sub-digital objects for transmission throughtwo or more intermediaries. Here, in a particular embodiment, asub-digital object may range in size from being as large as the largerdigital object, as small as a null object containing no data, or of anintermediate size containing, for example, packet, sub-packet,aggregation of packets and/or an aggregation of bits forming thesub-digital object. According to an embodiment, although claimed subjectmatter is not limited in this respect, sub-digital objects forming adigital object may be independently transmitted through a datatransmission network to a destination using the same or different paths.Subject to any QoS requirements, for example, intermediaries may bid forthe service of forwarding individual sub-digital objects of a largerdigital object as described herein. Here, for example, a digital objectmay be sufficiently large such that it may be desirable to split thedigital object into one or more sub-digital objects, for example atsource node and/or at one or more of intermediary nodes, where one ormore of the sub-digital objects may be provided with its own individualrouting requirements, quality of service, routing paths, and so on, andwhere the sub-digital objects may be reassembled at one or more ofintermediary nodes and/or one or more of destination nodes. Such asub-digital object concept in one or more embodiments may be analogousto data transfer utilizing packets, where the sub-digital objects may beat a higher level of organization that a packets, but may be at a lowerlevel of organization that of a larger digital object. For example, amultimedia object may be split into a video sub-digital object and anaudio sub-digital object, and/or a multimedia object may be split into asub-digital objects corresponding to the scenes contained in themultimedia object, although the scope of claimed subject matter is notlimited in this respect. An example of such a digital object that may besuitable for being split up into one may be where the digital object isa movie. In one or more embodiments, a transmission of such an objectmay include a multiple input, multiple output (MIMO) transmission systemand/or a spatial division, multiple access system, for example where twoor more sub-objects may be transmitted in parallel in two or more links.In one particular embodiment, a network that may be suitable forsplitting a digital object into one or more sub-digital objects maycomprise at least a portion of the network operating in compliance withan Institute of Electrical and Electronics Engineers (IEEE) 802.16 typestandard such as a WiMax type standard, although the scope of claimedsubject matter is not limited in this respect.

As in data transmission network 25 illustrated above, an intermediary112 may comprise one or more routers (such as router 28, for example) toforward data packets to a destination node. Also, data transmissionnetwork 100 may employ MPLS and select particular intermediaries forforwarding a digital object to destinations.

In the particular embodiment shown in FIG. 3, a single intermediary 112b may be capable of forwarding a digital object from ISP 110 todestination nodes coupled to any of the ISPs 116 a, 116 b and/or 116 c.On the other hand, neither intermediary 112 a nor intermediary 112 cmay, by itself, be capable of forwarding a digital object to destinationnodes coupled to all three ISPs 116 a, 116 b and 116 c. To forward thedigital object to destination nodes coupled to all three ISPs, the ISP110 and/or source node 102 may select either the intermediary 112 b, orintermediaries 112 a and 112 c.

According to embodiments of data transmission networks shown in FIG. 1and/or FIG. 3, an intermediary may incur a cost for forwarding a digitalobject from in at least a portion of a data transmission network. Tooffset such a cost, an intermediary may receive compensation from aparty associated with a source node, ISP and/or destination in exchangefor forwarding a digital object over a portion of the network. Accordingto an embodiment, an intermediary may provide a bid specifying termsunder which the intermediary would forward a digital object over atleast a portion of a data transmission network. A party that is tocompensate an intermediary may select from among multiple bids for thebusiness of forwarding the digital object over at least a portion of thenetwork. However, this is merely an example embodiment and claimedsubject matter is not limited in these respects.

According to an embodiment, any node such as intermediary nodes and/orISP acting on behalf of another node such as source node, intermediarynodes, ISP and/or destination node 118, for example, may requesttransmission of a digital object. Likewise, a source node and/ordestination node may together request and/or otherwise agree to transmita digital object, for example as a result of a handshake between thesource node and/or destination node, and/or between at least one of thesource node and/or destination node, intermediary nodes, and/or one ormore proxy nodes. In one or more embodiments, a handshake may refer to achallenge handshake authentication protocol (CHAP) type authenticationbetween a network server and a client device, although the scope ofclaimed subject matter is not limited in this respect. A handshake mayoccur via direct communication between two or more nodes, and/oralternatively a handshake may occur via indirect communication betweentwo or more nodes, for example using electronic mail or other suitableprotocol. In one or more embodiments, a “proxy server” may refer to aserver, node, and/or client device that may operate to provide,implement, process and/or intercept requests on behalf of given otherserver, node, and/or client device, and/or to operate interposed betweena first server, node, and/or client device and second server, node,and/or other client device. Such a proxy sever may operate to provide,implement, process, and/or intercept a request on behalf of and/or inlieu of at least one of such a server, node, and/or client device,and/or may operate as an agent-of at least one of such a server, node,and/or client device, and in one or more embodiments may appear to otherservers, nodes, and/or client devices on a data transmission network asthough it were in fact the server, node, and/or client device for whichsuch a proxy may be acting as an agent thereof. Such a proxy serverand/or an agent may be implemented on any one or more of a source node,source ISP, intermediary nodes, destination ISP, and/or destinationnodes, and/or on other nodes on a data transmission network. In one ormore embodiments, such a proxy server and/or agent may be utilized toimplement one or more specialized functions as part of the overallprocess and/or processes for transmitting a digital object via a datatransmission network. For example, if a digital object were a largersized object that could be partitioned into one or more smaller sizedsub-digital objects and/or packets for more efficient transmission, aproxy server dedicated to such partitioning of a digital object may beutilized. Other such specialized functions of a proxy server and/oragent may exist, for example compression, decompression, recombining,and so on. However, these are merely examples of how a proxy serverand/or agent may operate on a data transmission network, and the scopeof claimed subject matter is not limited in these respects.

FIG. 4 is a flow diagram illustrating a process 200 to initiatetransmission of a digital object from a source node according toembodiments of data transmission networks 25 and 100. All or someportions of process 200 may be performed by logic at a source node. Inone particular embodiment, as illustrated below, portions of process 200may be performed at a proxy server (e.g., at an ISP or otherunidentified node in a data transmission network) that is capable ofcommunicating with a source node and one or more intermediaries. Atblock 202, a source node may form a digital object for transmission toone or more destination nodes. In a particular embodiment, a computeroperator may form the digital object through interactions with agraphical user interface (GUI) of a computing platform associated withand/or coupled to the source node. However, this is merely an example ofhow a digital object may be formed and claimed subject matter is notlimited in these respects. In one particular embodiment, the digitalobject may be formatted into one or more data packets according to anetwork protocol such as the IP protocol. As such, the one or more datapackets may comprise a header portion with a destination IP addressassociated with a destination node. If the digital object is to betransmitted to more than one destination node, block 202 may formatmultiple sets of data packets for corresponding destination nodes withcorresponding destination IP addresses. According to particularembodiments, although claimed subject matter is not limited in theserespects, such multiple sets of data packets may be copied fortransmission to -corresponding multiple destination at a source node,ISP and/ or intermediary. However, these are merely examples of wherecopies of data packets of digital object may be made for transmission tomultiple destinations, and claimed subject matter is not limited inthese respects.

A particular intermediary in a data transmission network may or may notbe capable of transmitting a digital object to a destination node. Inthe particular embodiment of data transmission network 100 shown in FIG.3, for example, there is no link connecting intermediary 112 a with ISP116 c, and no link connecting intermediary 112 c with ISP 116 a.Accordingly, intermediary 112 a may be deemed incapable of forwardingdigital objects to destination nodes 118 c, 120 c and/or 122 c.Likewise, intermediary 112 c may be deemed incapable of forwardingdigital objects to destination nodes 118 a, 120 a and 122 a. In otherembodiments, an intermediary may or may not be capable of forwarding adigital object to a destination based, at least in part, on otherfactors regardless of whether the intermediary is connected to a sourceand/or destination node by a link. Here, for example, such anintermediary node may be deemed incapable based, at least in part, onknown equipment failures, inability to forward the digital objectaccording to a desired QoS, and the like. However, these are merelyexamples of how and/or why an intermediary may be incapable offorwarding a digital object to destination and claimed subject matter isnot limited in these respects.

At block 204 the source node and/or a proxy server may identifyintermediaries that are capable of forwarding a digital object to one ormore destination nodes. In one embodiment, a source node and/or proxyserver may identify intermediaries that are capable of forwarding adigital object based, at least in part, on information in a database.Such a database may be maintained at a source node and/or proxy serverand may identify particular intermediaries that are connected to thesource node and capable of receiving digital object for forwarding. Sucha database may also associate information with intermediaries such as,for example, capability to forward digital objects while achieving acertain QoS, operational status (e.g., functioning, down formaintenance, malfunctioning, etc.) and information indicative ofdestinations to which intermediaries may forward digital objects.However, this is merely an example of information that may be associatedwith intermediaries in a database for the purpose of identifyingintermediaries which are capable of forwarding digital object to adestination and claimed subject matter is not limited in this respect.

At block 206, a source node and/or proxy server may initiate thetransmission of bid requests to one or more intermediaries, requestingbids for a service of forwarding the digital object to one or moredestination nodes. Here, a bid request may be transmitted through anin-band management channel of links that carry data packets of digitalobjects transmitted between a source and an intermediary. Alternatively,a bid request may be transmitted to the intermediary in a link that isseparate from a link carrying digital objects. A source node and/orproxy server may transmit bid requests to intermediaries according toany one of several communication protocols. In one particularembodiment, for example, a source node and/or proxy server may transmitbid request in one or more data packets using a user datagramprotocol/Internet protocol (UDP/IP). However, these are merely examplesof how a source node and/or proxy server may transmit a bid request toone or more intermediaries and claimed subject matter is not limited inthese respects.

According to an embodiment, a digital transmission form (DTF) maycomprise metadata associated with a digital object that may beseparately stored, represented and/or transmitted independently of theassociated digital object. In particular embodiments, although claimedsubject matter is not limited in this respect, DTFs associated withdigital objects may be transmitted among nodes in a data transmissionnetwork (e.g., source node, ISPs and/or intermediaries) using the datapaths used for transmitting the digital objects. In alternativeembodiments, DTFs associated with digital objects may be transmittedamong nodes in a data transmission using data paths that are distinctfrom data paths used for transmitting digital objects. However, theseare merely examples of how DTFs may be transmitted among nodes in a datatransmission network and claimed subject matter is not limited in theserespects.

According to a particular embodiment, a bid request may be formatted asDTF that may be transmitted in one or more messages according to anegotiation protocol. Here, a DTF may comprise predefined fields thatspecify terms of a bid request for the service of transmitting a digitalobject to a destination node. Such predefined fields may be used forproviding information to a bidding party such as, for example, size ofthe digital object to be transmitted (e.g., in bits, bytes, cells,packets, etc.), destination address(es), QoS, compression format,security, encryption, billing account number and/or the like.Alternatively, a DTF may comprise a reference to a pre-defined fielddefinition schema and/or the schema itself, and/or the field valuesexpressed in a format, e.g., XML. However, these are merely examples ofpredefined fields that may be used in DTF for providing a bid requestand claimed subject matter is not limited in these respects.

As pointed out above, a DTF may facilitate a process of bidding for aservice of forwarding an associated digital object to a destination. Inaddition to forwarding digital objects as consequence of bidding, inparticular embodiments, although claimed subject matter is not limitedin this respect, a data transmission network may permit the forwardingof other data traffic that does not require acceptance of a bid as aconsequence of formation and/or transmission of a DTF. Here, forexample, parties may have existing agreements and/or routes to forwardtraffic that obviates a need for bidding. However, this is merely anexample of how a data transmission network may forward data trafficwithout the use of a DTF and claimed subject matter is not limited inthis respect.

As discussed above, a source node may forward a digital object to morethan one destination node. Also, as pointed out above, certainintermediaries may not be capable of forwarding a digital object to allintended destination nodes. Accordingly, in a particular embodiment,different bid request messages may be forwarded to differentintermediaries based, at least in part, on known abilities of particularintermediaries in forwarding the digital object to particulardestinations (e.g., as determined at block 204). Referring to theexample of FIG. 3, according to a particular embodiment, source node 102may format a digital object for transmission to destination nodes 118 a,118 b and 118 c. Intermediary 112 a may receive one or more bid requestsfor forwarding the digital object to destination nodes 118 a and 118 b,but not for forwarding the digital object to destination node 118 c.Likewise, intermediary 112 c may receive one or more bid requests forforwarding the digital object to destination nodes 118 b and 118 c, butnot for forwarding the digital object to destination node 118 a.

In embodiments illustrated above, block 204 may identify one or moreintermediaries that are capable of forwarding a digital object to adestination node. In alternative embodiments, however, block 206 mayforward bid requests to any identifiable intermediary nodes, regardlessof whether such intermediary nodes are determined to be capable ofproviding a desired service. This enables the intermediaries todetermine for themselves as to whether they are capable forwarding thedigital object to the destination under the terms of the bid.Accordingly, use of block 204 in identifying capable intermediaries ismerely an optional embodiment, and claimed subject matter is not limitin these respects.

After a time period following transmission of bid requests tointermediaries at block 206, source node and/or proxy server may receiveone or more bids from one or more intermediaries expressing an abilityand/or willingness to forward a digital object to one or moredestination according to terms set forth in the one or more receivedbids. Such terms in the bid may include, for example, price, QoS,expected delivery time and/or maximum latency. However, these are merelyexamples of terms that an intermediary may provide in a bid for thetransmission of a digital object to one or more destination, and claimedsubject matter is not limited in this respect.

Upon receipt of one or more bids from one or more intermediaries, asource node and/or proxy server may process received bids at block 208.Block 208 may select one or more intermediaries to forward the digitalobject to one or more destination nodes based, at least in part, on oneor more received bids. In one particular embodiment, to forward adigital object to a particular destination node, block 208 may select anintermediary specifying a lowest price in its bid for this service.Alternatively, block 208 may select an intermediary specifying a lowestbid for a minimum specified QoS associated with forwarding the digitalobject to the destination node. In one particular embodiment, althoughclaimed subject matter is not limited in this respect, acceptance and/orrejection of a bid, and/or termination of a biding process may bedetermined, at least in part, on a predetermined negotiation protocol.Here, for example, such a negotiation protocol may determine a formatfor bids, mechanisms to reject bids arriving late (e.g., after a timeoutperiod), rejection of bids because a party soliciting a bid haspre-existing relationships with other intermediaries to provide aservice of forwarding a digital object, and/or the like.

A negotiation protocol may also define multiple message types including,for example, bid requests, bids, acknowledgement of a bid request and/orbid, rejection and/or acceptance of a bid, broadcasting results of a bidrequest and subsequent bids, and/or changes for future bidding for theservice of forwarding a digital object. However, these are merelyexamples of messages that may be defined as part of a negotiationprotocol and claimed subject matter is not limited in these respects.

Upon selecting an intermediary to forward a digital object to adestination node, the source node and/or proxy server may initiate theselected intermediary to forward data packets carrying the digitalobject to one or more destination nodes. In a particular embodimentemploying the aforementioned MPLS protocol, for example, the source nodeand/or proxy server may intiate a node in a data transmission network(e.g., source node or ISP connected to source node) to act as an LER.Here, such an LER may associate data packets carrying a digital objectwith a switch label identifying the digital object and how the digitalobject is to be processed by a recipient LSR. The LER may then forwarddata packets carrying the digital object to an ingress communicationport of router acting as an LSR and which is owned, leased, controlledand/or operated by the selected intermediary. However, this is merely anexample of how such a selected intermediary may be set to forward datapackets carrying a digital object to a destination node and claimedsubject matter is not limited in this respect.

FIG. 5 is a flow diagram illustrating a process embodiment 300 to actupon a bid request received at an intermediary according to anembodiment. Process embodiment 300 may be executed by logic associatedwith an intermediary such as, for example, a computer system asillustrated above. However, this is merely an example of logic that iscapable of executing a process to act upon a bid request and claimedsubject matter is not limited in this respect. According to anembodiment, an intermediary may receive a message comprising a bidrequest (e.g., in the form of a DTF) at block 302. As described above, abid request may be transmitted from a source node and/or proxy serveraccording to a communication protocol using an in-band messagetransmitted in links for transmitting digital objects. As such, anintermediary may receive a bid request at an ingress communication portof a router that is capable of receiving data packets carrying digitalobjects from a source node. Alternatively, an intermediary may receive abid request at a communication port that is coupled to a link of adifferent network that is dedicated for transmitting and/or receivingmessages comprising bid requests, bids and/or other management messages.However, these are merely examples of how a bid request may be receivedat an intermediary and claimed subject matter is not limited in thisrespect.

Block 304 may determine terms for a bid for a service of forwarding adigital object to a destination node. As illustrated above, such a bidmay specify terms and/or conditions under which an intermediary mayagree to for the business of forwarding a digital object to adestination node. Block 304 may determine these terms and/or conditionsbased, at least in part, on capital equipment costs (e.g., for routersand related support equipment), operating costs (including, for example,asset maintenance, rent, power, personnel), current and/or predictedcapacity, current and/or predicted asset utilization, prior experienceand/or history, pre-existing contracts with other parties, vendorpreference, anticipated bid behavior from competing intermediaries forthe transmission of the digital object to the destination, anticipateddemand and/or ability to provide a particular QoS for the transmissionof the digital object. However, these are merely examples of informationthat an intermediary may utilize in determining terms for a bid for thetransmission of a digital object to a destination node and claimedsubject matter is not limited in this respect.

Following determining terms of a bid at block 304, an intermediary maytransmit the bid to a source node and/or proxy server at block 306. Sucha bid may be transmitted to a source node and/or proxy server through acommunication port which is capable of receiving digital objects fromthe source node and/or transmitting digital objects to destinations inthe data transmission network. Alternatively, such a bid may betransmitted in an out-of-band message in a different data link. However,these are merely examples of links that may be used for transmitting amessage comprising a bid and claimed subject matter is not limited inthese respects. In another embodiment, the message comprising a bid maybe transmitted according to any one of several protocols such as, forexample, UDP/IP and/or a proprietary protocol. However, this is merelyan example of a communication protocol that may be used for thetransmission of a bid to a source node and/or proxy server and claimedsubject matter is not limited in this respect.

It should be understood that, according to a particular embodiment, anintermediary receiving a bid request at block 302 may choose not torespond to the bid request for any one of several reasons such as, forexample, an inability to forward the digital object to a specifieddestination node and/or insufficient capacity to satisfy requested QoSservice, a policy to not do business with this particular solicitor orclass of solicitors and/or the like. Alternatively, an intermediary maytransmit a message to a source node and/or proxy server indicating thatthe intermediary will not bid for the business of forwarding the digitalobject at issue. In another embodiment, an intermediary may alsotransmit a reason for not participating in the bidding process.

Following transmission of a bid at block 306, process 300 may wait for aresponse from a source node and/or proxy server indicating that thetransmitted bid has either been accepted or rejected. Such an acceptancemessage from a source node and/or proxy server may take the form of amessage transmitted in-band along with digital objects or as anout-of-band message in a separate network. In one embodiment, forexample, diamond 308 may determine acceptance of a bid upon receipt ofone or more data packets at an ingress communication port carrying atleast a portion of the digital object and addressed to the destinationnode, providing an implied acceptance message. In an alternativeembodiment, diamond 308 may determine a rejection of the bid if no suchdata packets carrying at least a portion of the digital object arereceived at an ingress communication port within a predetermined periodfollowing transmission of the bid at block 306. In another alternativeembodiment, the diamond 308 may determine whether the bid is accepted orrejected based on an explicit acceptance message or rejection messagereceived from an in-band and/or out-of-band data link. However, theseare merely examples of how an intermediary may determine acceptanceand/or rejection of a bid for a service of forwarding a digital objectand claimed subject matter is not limited in these respects.

In response to an indication that a bid has been accepted, diamond 308may enable forwarding a digital object to a destination node at block310. According to an embodiment in which an intermediary comprises oneor more routers capable of acting as LSRs in an MPLS network, forexample, block 3 1 0 may enable one or more routers in an LSP to forwarddata packets to one or more destination nodes. Data packets identifiedas carrying the digital object based upon associated switch labels maybe forwarded through the LSP toward the one or more destination nodes.According to an embodiment, the intermediary may receive data packetscarrying a digital object at an ingress communication port of an initialrouter. Data packets carrying a digital object along an LSP (or possiblymultiple LSPs for more than one destination node) may traverse one ormore routers until being transmitted from an egress port of a finalrouter toward the destination node. In an alternative embodiment, anInterior Gateway Protocol (IGP) may be used for routing traffic.However, these are merely examples of how an intermediary may enableforwarding of a digital object to a destination and claimed subjectmatter is not limited in these respects.

In response to an indication that a bid has been rejected, diamond 308may inhibit forwarding a digital object to the destination node at block312 if the bid is rejected. In one particular embodiment, for example,block 312 may inhibit forwarding data packets received at an ingressport of a router by, for example, dropping packets being received at aningress port of a router without informing a sender. However, this ismerely an example of how an intermediary may inhibit the forwarding of adigital object to a destination node and claimed subject matter is notlimited in these respects.

As pointed out above, a bid request and/or related bid may relate toforwarding a digital object to multiple destination nodes. Here, in aparticular embodiment, a source node and/or proxy server may accept aportion of a bid for forwarding a digital object to one destination nodeand reject a portion of the bid for forwarding the digital object to oneor more other destination nodes. Accordingly, in this particularembodiment, diamond 308 may enable forwarding of a digital object tosome destination nodes (relating to an accepted portion of a bid) andinhibit forwarding of the digital object to other destination nodes(relating to a rejected portion of the bid). However, this is merely anexample of how an intermediary may process a partial acceptance of a bidfor a service of forwarding a digital object and claimed subject matteris not limited in these respects.

FIG. 6 is a schematic diagram of a data transmission network 400 fortransmitting a digital object from a source node to one or moredestination nodes through two or more intermediaries. A source node 402,coupled to data transmission network 400 through ISP 410, may desireforwarding a digital object to a destination node coupled to ISP 416.ISP 410 may forward a digital object to intermediaries 412 a, 412 band/or 412 c without any intervening network hops. However,intermediaries 412 a, 412 b and/or 412 c may not necessarily be capableof forwarding a digital object to a destination node without assistanceof one or more downstream intermediaries. Here, no single intermediary412 a, 412 b and/or 412 c may necessarily be capable of forwarding adigital object to ISP 416 without forwarding the digital object throughat least one downstream intermediary 413 a, 413 b, 413 c, 413 d, 413 e,413 f and/or 413 g. Likewise, no single intermediary 413 a, 413 b, 413c, 413 d, 413 e, 413 f and/or 413 g may be capable of forwarding adigital object to ISP 416 without routing the digital object through anintermediary 415 a, 415 b and/or 415 c.

In response to a request for a bid for the service of forwarding adigital object from ISP 410 to a destination node 404, 406 and/or 408,according to a particular embodiment, an intermediary 412 a, 412 band/or 412 c may provide a bid comprising terms which are based, atleast in part, upon a cost associated with forwarding the digital objectthrough one of downstream intermediaries 413 a through g. Whileexecuting process 300 (FIG. 5), according to a particular embodiment forresponding to the request for a bid, at block 304 an intermediary 412 a,412 b and/or 412 c may transmit a bid request to one or more downstreamintermediaries 413 a through g. Upon receiving bids from one or more ofdownstream intermediaries, intermediary 412 a, 412 b and/or 412 c maydetermine terms for a bid for the transmission of the digital objectreceived from the ISP 410 based, at least in part, on terms from one ormore bids received from one or more downstream intermediaries.Intermediary 412 a, 412 b and/or 412 may then complete process 300 asillustrated above. In determining bids in response to bid requests fromintermediaries 412 a, 412 b and/or 412 c, intermediaries 413 a through gmay similarly request bids of and/or receive bids from downstreamintermediaries 415 a, 415 b and/or 415 c as illustrated above.

FIG. 7 is a flow diagram illustrating a process embodiment 450 to actupon a bid request received at an intermediary according to anembodiment. According to particular embodiment, process embodiment 450may be executed by one or more of intermediaries 412 in response to abid request from a source node and/or proxy server. In anotherembodiment, process embodiment 450 may be executed by one or more of thedownstream intermediaries 413 in response to a bid request from anintermediary 412. At block 452, an intermediary may receive a bidrequest as illustrated above with reference to block 302 of FIG. 5. Inthe case of receiving a bid request at a downstream intermediary 413,however, it should be understood that such a bid request may originatefrom an intermediary 412. Block 454 may identify one or more downstreamintermediaries capable of transmitting the digital object to thedestination node as illustrated above with reference to block 204 ofprocess 200.

Block 456 may formulate and transmit a downstream bid request todownstream intermediaries identified in block 454. The terms set forthin such a bid request may be based, at least in part, upon terms setforth in one or more bid requests received at block 452. In a particularembodiment, for example, a bid request formulated at block 456 maycharacterize a digital object, specify one or more destination nodes andindicate how the digital object is to be transmitted to the one or moredestination nodes as described above with reference to block 206 in FIG.4. Bid requests formulated at block 456 may then be transmitted to oneor more downstream intermediaries as an in-band and/or out-of-bandmessage as illustrated above with reference to block 206 above.

At block 458, an intermediary may receive one or more bids in responseto bid requests transmitted at block 456. Such bids received at block458 may express terms such as those expressed in bids received at block208 as illustrated above. Here, process embodiment 450 may wait forresponses following transmission of the bid requests at block 456 for apredetermined period following a transmission of one or more bidrequests. Then, block 460 may determine terms for one or more bids torespond to the bid request received at block 452. Terms set forth inthese bids may be based, at least in part, upon terms set forth in oneor more bids received at block 456. Here, for example, block 460 maydetermine a price associated with a bid responsive to the bid requestreceived at block 452 based, at least in part, a cost associated withone or more of the bids received at block 458. However, these are merelyexamples of how terms of a bid for a service of transmitting a digitalobject to a destination may be determined and claimed subject matter isnot limited in this respect.

The discussion above illustrates a process by which intermediaries maybid for the business of providing a service of forwarding digitalobjects to destination nodes. In particular embodiments, a datatransmission network may transport digital objects in data packets overlinks connecting a source node and/or ISP with intermediaries, andconnecting intermediaries with destination nodes. In additionalembodiments, a separate network, apart from a data transmission networkused for forwarding digital objects, may facilitate an exchange ofmanagement messages such as, for example, bid requests, bids, and theirstatus. This may enable centralized deployment of the activities ofbidding and billing for the services of forwarding digital objects overthe data transmission network.

FIG. 8 is a schematic diagram of a data transmission network 500comprising a first network to transmit a digital object from a sourcenode to a destination node, and second network to facilitate biddingamong intermediaries. A source node 502 may be coupled to the datatransmission network 500 by an ISP 510. Source node 502 may transmit adigital object to one or more destination nodes 518 through ISP 510,intermediaries 512 and/or ISP 516. For the purpose of illustration,nodes are connected by data links of the first network represented withsolid lines and nodes are connected by data links of the second networkrepresented by broken lines. According to a particular embodiment, datalinks represented by solid lines are capable of transmitting a digitalobject toward a destination over a corresponding portion of the firstnetwork. Also, data links represented by broken lines may be capable oftransmitting control messages, such as, for example, bid requests, bidsand acceptance messages, between a server 522 and other nodes in thedata transmission network 500.

According to an embodiment, source node 502 may transmit bid requests tointermediaries 512 for a service of forwarding a digital object to oneor more destination nodes 508 as discussed above. The intermediaries 512may also respond to such bids for this service as discussed above. Inthis particular embodiment, however, server 522 may communicate withsource node 502, ISP 510 and/or intermediate nodes through data links inthe second network to, among other things, transmit bid requests toand/or receive bids from intermediaries 512.

According to an embodiment, an agent process embodiment 520 may executeon one or more intermediaries 512 to communicate with server 522. Forexample, in a particular embodiment, an instance of agent processembodiment 520 may be executed by logic such as machine-readableinstructions capable of executing on a computer system operated by oneor more intermediaries 512. Also, intermediaries 512 may compriseout-of-band communication ports which are capable of communicating onthe second network that are distinct from communication ports used forforwarding digital objects on the first network. In a particularembodiment, agent process 520 may communicate with server 522 throughsuch out-of-band communications ports.

According to an embodiment, links of the second network may comprise anyone of several types of transmission media such as, for example, any ofthe aforementioned cabling and/or wireless mediums. Again, however,these are merely examples of transmission media that may used fortransmitting messages in the second network and claimed subject matterin not limited in these respects. According to a particular embodiment,messages may be transmitted in links of the second network using any oneof the aforementioned data link layer protocols, and may be formattedfor transmission on the second network according to any one of theaforementioned network protocols. Again, however, these are merelyexamples of data link and/or network protocols and claimed subjectmatter is not limited in these respects.

According to an embodiment, a process of bidding for the service offorwarding a digital object from source node 502 to one or moredestination nodes 518 may be governed, at least in part, by server 522and/or agent process embodiment 520. FIG. 9 is a flow diagramillustrating a process 600 to initiate transmission of a digital objectto one or more destination nodes according to an embodiment of datatransmission network 500. In a particular embodiment, for example,process embodiment 600 may be performed by logic at the source node 502and/or ISP 510. At block 602, a digital object may be formulated asillustrated above with reference to block 202 of FIG. 4. However, ratherthan forwarding bid requests directly to intermediaries, process 600 mayforward a bid request to sever 522 (e.g., over the second network). Asillustrated below with reference to FIG. 10, server 522 may thenfacilitate a bidding process among intermediaries 512 for the service offorwarding the digital object to a destination node and selecting anintermediary for forwarding the digital object. Block 606 may receiveinformation (e.g., over the second network) from server 522 whichenables forwarding of the digital object to the selected intermediary.For example, block 606 may receive a network address and/or some otheridentifier associated with a selected intermediary 512 from which theISP 510 may transmit data packets carrying a digital object to theselected intermediary 512. Block 608 may then initiate transmission ofthe digital object to a selected intermediary based, at least in part,upon the forwarding instructions received at block 606.

FIG. 10 is a flow diagram illustrating a process embodiment 700facilitating bidding for the service of forwarding a digital object toone or more destination nodes according to a particular embodiment of adata transmission network of FIG. 8. Block 702 may receive a bid requestfrom source node 502 and/or ISP 510 from the second network (e.g.,transmitted at block 604). Block 704 may then broadcast the bid requestto one or more intermediaries 512 over the second network. Upon receiptof bid requests from the second network, an instance of agent 520executing on an associated intermediary may process the bid request andprovide a bid as illustrated above with reference to FIG. 5. In thisparticular embodiment, however, the instance of agent 520 may receivebid requests from, and transmit bids to server 522 over the secondnetwork.

In one embodiment, process embodiment 700 may initially identifyintermediaries 512 which may be capable of forwarding a digital objectto the destination as illustrated above with reference to block 204(FIG. 4), and limit transmission of bid requests at block 704 to suchcapable intermediaries 512. Alternatively, process embodiment 700 maymerely rely on responses to the bid requests and/or absences ofresponses to determine the capabilities of the intermediaries 512 asillustrated above.

Upon receiving bids from instances of agent 520, process embodiment 700may select one or more intermediaries 512 to forward a digital object toone or more destinations, based, at least in part, upon terms set forthin the received bids as illustrated above with reference to block 208(FIG. 4). Block 708 may then transmit information to be used inforwarding the digital object (e.g., network address(es) of selectedintermediary(ies)) over the second network to source node 502 and/or ISP510 based, at least in part, on the one or more selected intermediaries.

According to an embodiment, server 522 and/or agent process embodiment520 may maintain billing information for client source nodes and/orISPs. For example, server 522 may maintain an account of charges owed tointermediaries for forwarding digital objects which have accrued as aresult of the bidding process described above or otherwise. In aparticular embodiment, block 710 may update the account of source node502 and/or ISP 510 according to terms of a bid provided by theintermediary 512 selected to forward the digital object to thedestination node. For example, server 522 may associate charges with anaccount number provided in a field of a DTF as part of a bid requestreceived at block 702. However, this is merely an example of maintainingand/or updating an account for charges accrued for the forwarding ofdigital objects and claimed subject matter is not limited in theserespects.

In another particular embodiment, server 522 may coordinate periodicinvoicing of accrued charges to nodes that have used the services ofintermediaries in forwarding objects in the data transmission network.Server 522 may also facilitate connection charges and/or payment tointermediaries having performed the services of forwarding the digitalobjects. In one embodiment, server 522 may maintain credit accounts forparties (e.g., source nodes and/or ISPs) that may employ the services ofintermediaries in forwarding digital objects. Here, server 522 maycharge payment to intermediaries for services performed for partiesagainst the parties' credit accounts. However, these are merely examplesof how server 522 may coordinate period invoicing for services performedby intermediaries and claimed subject matter is not limited in theserespects.

As illustrated in FIG. 3 above, a source node may forward a digitalobject to multiple destination nodes over multiple paths. A firstintermediary may be selected for forwarding the digital object to one ormore destination nodes over a first path and a second intermediary maybe selected for transmitting the digital object to one or more otherdestination nodes over a second path. It should be apparent that theembodiments of FIG. 8 through 10 may facilitate bidding amongintermediaries for the service of forwarding the digital object inmultiple paths to multiple destinations. Here, server 522 may provideinformation for forwarding the digital object at block 708 to two ormore intermediaries corresponding to the multiple paths.

FIGS. 6 and 7 above illustrate a method and/or system for thetransmission of a digital object to a destination node by forwarding thedigital object over two or more intermediaries. Here, according to aparticular embodiment, the second network may couple server 522 to asource node and/or ISP as well as intermediaries capable of receiving adigital object from the ISP. In response to bid requests from server522, instances of agent 520 (executing on the intermediaries coupled tothe second network) may obtain bids from one or more downstreamintermediaries (not shown). Instances of agent 520 may then determineterms for bids for the service of forwarding the digital object to thedestination node as illustrated above in process embodiment 450 andtransmit the bids to server 522 over the second network. Upon acceptanceof one or more of the bids, server 522 may transmit one or moreacceptance messages to one or more instances of agent 520 over thesecond network. Alternatively, as illustrated above, an acceptance maybe implied upon receipt of one or more data packets at an intermediarycarrying all or a portion of the digital object. Upon an indication ofsuch an acceptance (explicit and/or implied), an instance of agent 520may accept one or more of said bids received from one or more downstreamintermediaries as illustrated above.

While there has been illustrated and described what are presentlyconsidered to be example embodiments, it will be understood by thoseskilled in the art that various other modifications may be made, andequivalents may be substituted, without departing from claimed subjectmatter. Additionally, many modifications may be made to adapt aparticular situation to the teachings of claimed subject matter withoutdeparting from the central concept described herein. Therefore, it isintended that claimed subject matter not be limited to the particularembodiments disclosed, but that claimed subject matter may also includeall embodiments falling within the scope of claimed subject matter, andequivalents thereof.

1. A method comprising: receiving a first bid request for forwarding adigital object to a destination node; transmitting a second bid requestto one or more intermediaries; receiving one or more bids, provided inresponse to said second bid request, from said one or moreintermediaries; and transmitting a bid in response to said first bidrequest based, at least in part, on terms expressed in said received oneor more bids.
 2. The method of claim 1, and further comprisingidentifying one or more intermediaries capable of forwarding the digitalobject to said destination.
 3. The method of claim 1, and furthercomprising: receiving a message indicative of an acceptance of saidtransmitted bid; and transmitting a message to one or more selected onesof said intermediaries to accept at least one of said bids receivedprovided in response to said second bid request.
 4. The method of claim1, and further comprising: receiving said digital object from a sourcenode; and forwarding said digital object to at least one of said one ormore identified intermediaries.
 5. The method of claim 4, wherein saidforwarding said digital object to at least one of said one or moreidentified intermediaries further comprises: formatting said digitalobject into one or more data packets; associating said one or more datapackets with a switch label; and forwarding one or more of said datapackets to a label switch router.
 6. The method of claim 1, and furthercomprising receiving an indication of an acceptance of said transmittedbid.
 7. The method of claim 6, and further comprising enablingforwarding of the digital object to the destination node in response tosaid indication.
 8. The method of claim 6, and further comprisingtransmitting an acceptance message to at least one of said one or moreintermediaries in response to said indication.
 9. The method of claim 1,wherein said first bid request is received from a source node and/orInternet service provider.
 10. The method of claim 1, wherein said firstbid request is received from an intermediary.
 11. A method comprising:means for receiving a first bid request for forwarding a digital objectto a destination node; means for transmitting a second bid request toone or more intermediaries; means for receiving one or more bidsprovided in response to said second bid request from said one or moreintermediaries; and means for transmitting a bid in response to saidfirst bid request based, at least in part, on terms expressed in saidreceived one or more bids.
 12. The apparatus of claim 11, and furthercomprising means for identifying one or more intermediaries capable offorwarding the digital object to said destination.
 13. The apparatus ofclaim 11, and further comprising: means for receiving a messageindicative of an acceptance of said transmitted bid; and means fortransmitting a message to one or more selected ones of saidintermediaries to accept at least one of said bids received provided inresponse to said second bid request.
 14. The apparatus of claim 11, andfurther comprising: means for receiving said digital object from asource node; and means for forwarding said digital object to at leastone of said one or more identified intermediaries.
 15. The apparatus ofclaim 14, wherein said means for forwarding said digital object to atleast one of said one or more identified intermediaries furthercomprises: means for formatting said digital object into one or moredata packets; means for associating said one or more data packets with aswitch label; and means for forwarding one or more of said data packetsto a label switch router.
 16. The apparatus of claim 1 1, and furthercomprising means for receiving an indication of an acceptance of saidtransmitted bid.
 17. The apparatus of claim 16, and further comprisingmeans for enabling forwarding of the digital object to the destinationnode in response to said indication.
 18. The apparatus of claim 16, andfurther comprising means for transmitting an acceptance message to atleast one of said one or more intermediaries in response to saidindication.
 19. An article comprising: a storage medium comprisingmachine-readable instructions stored thereon to: process a first bidrequest for forwarding a digital object to a destination node; initiatetransmission of a second bid request to one or more intermediaries;process one or more bids, provided in response to said second bidrequest, received from said one or more intermediaries; and initiatetransmitting a bid in response to said first bid request based, at leastin part, on terms expressed in said received one or more bids.
 20. Thearticle of claim 19, wherein said storage medium further comprisesmachine-readable instructions stored thereon to identify one or moreintermediaries capable of forwarding the digital object to saiddestination.
 21. The article of claim 19, wherein said storage mediumfurther comprises machine-readable instructions stored thereon to:detect a message indicative of an acceptance of said transmitted bid;and initiate transmission of a message to one or more selected ones ofsaid intermediaries to accept at least one of said bids receivedprovided in response to said second bid request.
 22. The article ofclaim 19, wherein said storage medium further comprises machine-readableinstructions stored thereon to: receive said digital object from asource node; and initiate forwarding of said digital object to at leastone of said one or more identified intermediaries.
 23. The article ofclaim 22, wherein said storage medium further comprises machine-readableinstructions stored thereon to: format said digital object into one ormore data packets; associate said one or more data packets with a switchlabel; and initiate forwarding of one or more of said data packets to alabel switch router.
 24. The article of claim 19, wherein said storagemedium further comprises machine readable instructions stored thereon todetect an indication of an acceptance of said transmitted bid.
 25. Thearticle of claim 24, wherein said storage medium further comprisesmachine-readable instructions stored thereon to enable forwarding of thedigital object to the destination node in response to said indication.26. The article of claim 24, wherein said storage medium furthercomprises machine-readable instructions stored thereon to initiatetransmission of an acceptance message to at least one of said one ormore intermediaries in response to said indication.
 27. An apparatuscomprising a computing platform, the computing platform being adaptedto: process a first bid request for forwarding a digital object to adestination node; initiate transmission of a second bid request to oneor more intermediaries; process one or more bids, provided in responseto said second bid request, received from said one or moreintermediaries; and initiate transmitting a bid in response to saidfirst bid request based, at least in part, on terms expressed in saidreceived one or more bids.
 28. The apparatus of claim 27, wherein saidcomputing platform is further adapted to identify one or moreintermediaries capable of forwarding the digital object to saiddestination.
 29. The apparatus of claim 27, wherein said computingplatform is further adapted to: detect a message indicative of anacceptance of said transmitted bid; and initiate transmission of amessage to one or more selected ones of said intermediaries to accept atleast one of said bids received provided in response to said second bidrequest.
 30. The apparatus of claim 27, and further comprising a labelswitch router to: receive said digital object from a source node; andforward said digital object to at least one of said one or moreidentified intermediaries.
 31. The apparatus of claim 30, and furthercomprising a label switch router to: receive said digital object as oneor more data packets at an ingress communication port; associate saidone or more data packets with a switch label; and forward one or more ofsaid data packets to a downstream label switch router.
 32. The apparatusof claim 27, wherein said computing platform is further adapted todetect an indication of an acceptance of said transmitted bid.
 33. Theapparatus of claim 32, wherein said computing platform is furtheradapted to enable forwarding of the digital object to the destinationnode in response to said indication.
 34. The apparatus of claim 32,wherein said computing platform is further adapted to initiatetransmission of an acceptance message to at least one of said one ormore intermediaries in response to said indication.